feat: [OPE-1840] enable transaction history on Base - #2082
Merged
Conversation
Plug in the deployed pearl-transactions subgraph URL for Base (https://transactions-base.subgraph.autonolas.tech/), replacing the undefined placeholder that surfaced the 'not available on this network yet' state. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
atepem
force-pushed
the
precious/enable-base-transaction-history
branch
from
July 23, 2026 12:57
e40f517 to
c286e51
Compare
Clears three new high advisories against next <15.5.21: GHSA-m99w-x7hq-7vfj (DoS in App Router Server Actions), GHSA-89xv-2m56-2m9x (SSRF in Server Actions on custom servers), GHSA-p9j2-gv94-2wf4 (SSRF in rewrites). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
atepem
changed the title
Tanya-atatakai
approved these changes
Jul 23, 2026
Base's transactions proxy pins subgraph v0.0.7, whose schema is incompatible with the queries Pearl sends (FundsMovement.bondType removed, bond rows moved to a separate bondMovements ledger, OLAS sweeps pre-split into AGENT_OLAS_TO_MASTER, Service.id reshaped to registry bytes with the numeric id in serviceId) — every request failed GraphQL validation, so Base users saw the error state. Adds a per-chain schema-revision map beside the subgraph URL map (Base → v2; absent → v1), v2 query documents + Zod schemas verified against the live Base deployment, and service-boundary normalization back to the v1-shaped domain types (bond rows merged into fundsMovements, sweep rows dropped, service.id mapped from serviceId). Hooks and components are untouched and revision-agnostic; migrating Gnosis/Optimism to v0.0.7 later is a one-line map flip. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… gate) Clears GHSA-6g55-p6wh-862q (arbitrary file read via attacker-controlled sourceMappingURL), high, reachable via next>postcss. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
| // v0.0.6 (v1); Base pins v0.0.7 (v2) — its indexers no longer serve v0.0.6. | ||
| // When a chain's proxy migrates to v0.0.7, flip its entry here; absent | ||
| // entries default to v1. | ||
| export const TRANSACTION_HISTORY_SUBGRAPH_SCHEMA_BY_EVM_CHAIN: Partial< |
Contributor
There was a problem hiding this comment.
I'd rather extend TRANSACTION_HISTORY_SUBGRAPH_URLS_BY_EVM_CHAIN and rename, e.g. ```
TRANSACTION_HISTORY_SUBGRAPH_BY_EVM_CHAIN = {[EvmChainIdMap.Base]: {url: '...', version: 'v2'}}
| [EvmChainIdMap.Base]: 'v2', | ||
| }; | ||
|
|
||
| export const getTransactionHistorySchemaRevision = ( |
Contributor
There was a problem hiding this comment.
can't we just use object to know?
Tanya-atatakai
approved these changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Enables transaction history on Base — both Pearl Wallet → History and Agent Wallet → Balances & Assets.
Two parts:
TRANSACTION_HISTORY_SUBGRAPH_URLS_BY_EVM_CHAIN(wasundefined, surfacing the 'not available on this network yet' state).FundsMovement.bondTyperemoved, bond rows moved to a separatebondMovementsledger, OLAS sweeps pre-split intoAGENT_OLAS_TO_MASTER, andService.idreshaped to registry bytes (numeric id now inserviceId). Every request failed GraphQL validation → the tester's 'Error loading transaction history'. This PR adds a per-chain schema-revision map (Base → v2, absent → v1), v2 query documents + Zod schemas verified against the live Base deployment, and service-boundary normalization back to the v1-shaped domain types. Hooks and components are untouched and revision-agnostic; migrating Gnosis/Optimism to v0.0.7 later is a one-line map flip.Also bumps
next15.5.18 → 15.5.21 in both trees (three new high advisories tripped theyarn auditCI gate).Screenshots
Agent wallet
Pearl wallet
Verification
serviceIdtrap covered: v2 factories deliberately mismatch registry-bytesidvs numericserviceIdso any code reading.idfails tests.Out-of-scope follow-ups
config/chains.tsimportsparseEtherfrom the@/utilsbarrel, creating a latent import cycle (services here deep-import@/utils/transactionHistoryto avoid it). Worth switching that import to a deep path.🤖 Generated with Claude Code